-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to react router 7, typescript, and misc. refactoring #27
base: master
Are you sure you want to change the base?
Conversation
@@ -1,10 +1,12 @@ | |||
import type { Config } from 'tailwindcss'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Holding off on migrating to tailwind 4 — good news is that it supports plugins like typography (which we use) using a pure css syntax, so that's great
server/app.ts
Outdated
return next(); | ||
} | ||
|
||
const script = ` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider not doing this for bots — e.g. google crawlers - just return 0
return { | ||
commits: commits.map((commit) => ({ | ||
...commit, | ||
localDate: getPrettyDate(commit.timestamp, getClockOffset(request)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is for the service methods to be blind to the user's timezone — they're just responsible for fetching data, and we can transform it in the loaders
@sorokya did you get a chance to look at this yet? |
Pre-release steps (in dev and in prod):
bun upgrade
)Known issues:
rm -rf .react-router && bun run dev
to generate types again.